Adding a render test here: pietervdvn#1

Quality Gate failed

Failed conditions
75.0% Coverage on New Code (required ≥ 80%)

See analysis details on SonarQube Cloud

I've addressed the linter feedback, but, to be a bit blunt: why bother? The tooling can do this fully automatically. IMHO, automatically linting/formatting the codebase every now and then can be done with a script without having to do another round of feedback to me. (For context: I simply made the changes in the web editor without setting up the dev environment)

I've also merged (and fixed) in the render test by @wipfli

The tooling can do this fully automatically. IMHO, automatically linting/formatting the codebase every now and then can be done with a script without having to do another round of feedback to me.

You can run mvn spotless:apply in the tiles directory to do this automatically

The tooling can do this fully automatically. IMHO, automatically linting/formatting the codebase every now and then can be done with a script without having to do another round of feedback to me.

You can run mvn spotless:apply in the tiles directory to do this automatically

This implies that I installed the entire toolchain (spoilers: I didn't) and that I know this (spoilers: I didn't). This adds some more friction to the process of contributing here, which IMHO is useless. Just my 2 cents though.

Anyway, thanks for merging in my request and for maintining protomaps!